DRY up docs/README #4
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
yuyttenhove
approved these changes
Apr 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What I suggested after the last PR was closed: I condensed the integer arithmetic backend docs with the cargo features section and added your benchmarks table. I think it's much easier to grok than reading the % behind each feature. 😁
Misses
ibigtimings though.On that note
docs.rsandcrates.iohave full Smartypants support, i.e.--and---get turned into resp. unicode n and m dashes during conversion, But GH has not. So the README doesn't render as nice here.I think that's acceptable, use e.g.
inlyne. 😉